Method and Device for Subscribing to Radio Link Failure Report

ABSTRACT

The present invention provides a method and device for subscribing to an RLF report. An integration reference point manager configures a subscription condition for an RLF report for an integration reference point agent. The integration reference point manager obtains an RLF report that is sent by the integration reference point agent and satisfies the subscription condition. The present invention can avoid that a base station sends an RLF report obtained from a UE, to an IRPManager through an IRPAgent in a best-effort mode, thereby decreasing the load of information transferred between the IRPManager and the IRPAgent.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/168,724, filed on Jan. 30, 2014, which is a continuation ofInternational Application No. PCT/CN2o12/076741, filed on Jun. 12, 2012,which claims priorities to Chinese Patent Application No.201110219526.5, filed on Aug. 2, 2011 and Chinese Patent Application No.201110288467.7, filed on Sep. 26, 2011, all of which are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

Embodiments of the present invention relate to communicationtechnologies, and in particular, to a method and device for subscribingto a radio link failure report.

BACKGROUND

A radio link failure (RLF) is an abnormal link scenario that occurs onan air interface of a radio access network. When an RLF occurs on a userequipment (UE) in an active state in a current cell (that is, a sourcecell), the UE generates an RLF report, performs cell reselection, andinitiates a radio resource control (RRC) connection reestablishmentprocedure to a base station (that is, a target base station) controllinga selected cell (that is, a target cell). By using RRC ConnectionReestablishment Complete message, the UE may instruct the target basestation to obtain the RLF report. After obtaining the RLF report, thetarget base station may send the RLF report to a base stationcontrolling the source cell (that is, a source base station).

However, because the source base station or the target base station maysend the RLF report obtained from the UE, to an integration referencepoint manager (IRPManager) through an integration reference point agent(IRPAgent) in a best-effort mode, the load of RLF report informationtransferred between the IRPManager and the IRPAgent is heavy.

SUMMARY

Embodiments of the present invention provide a method and device forsubscribing to an RLF report, so as to decrease the load of informationtransferred between an IRPManager and an IRPAgent.

In a first preferred aspect, the present invention provides a method forsubscribing to an RLF report, including configuring, by an IRPManager, asubscription condition for an RLF report, for an IRPAgent. TheIRPManager obtains an RLF report that is sent by the IRPAgent andsatisfies the subscription condition.

In a first preferred implementation of the first preferred aspect,configuring the subscription condition for the RLF report includesinvoking, by the IRPManager, a Create Management Object operation forthe IRPAgent, for requesting the IRPAgent to create an RLF reportsubscription subcategory of a subnet category or a base station functioncategory. The IRPManager invokes a Set Management Object Attributesoperation for the IRPAgent, for requesting the IRPAgent to configure anattribute of the created RLF report subscription subcategory to a valueof an attribute corresponding to the subscription condition.

In a second preferred implementation of the first preferredimplementation of the first preferred aspect, a mechanism of obtainingthe RLF report that is sent by the IRPAgent by the IRPManager andsatisfying the subscription condition includes a file transfermechanism.

In a third preferred implementation of the first preferred aspect, theconfiguring, by the IRPManager, the subscription condition for the RLFreport, for the IRPAgent includes invoking a Subscribe Log operation forthe IRPAgent by the IRPManager, for subscribing to the RLF report fromthe IRPAgent, where a filter condition of the Subscribe Log operation isthe subscription condition.

In a fourth preferred implementation of the third preferredimplementation of the first preferred aspect, a mechanism of obtaining,by the IRPManager, the RLF report that is sent by the IRPAgent andsatisfies the subscription condition includes a notification logmechanism.

In a fifth preferred implementation of the first preferred aspect, theconfiguring, by the IRPManager, the subscription condition for the RLFreport, for the IRPAgent includes invoking, by the IRPManager, anActivate Signaling Trace Job operation for the IRPAgent, for requestingthe IRPAgent to generate a signaling trace job. A job type of thesignaling trace job is RLF reporting only. An input parameter of theActivate Signaling Trace Job operation is a value of an attributecorresponding to the subscription condition.

In a sixth preferred implementation of the fifth preferredimplementation of the first preferred aspect, a mechanism of obtaining,by the IRPManager, the RLF report that is sent by the IRPAgent andsatisfies the subscription condition includes a trace result reportingmechanism of a signaling trace job or a trace result reporting mechanismof a minimized drive test MDT job.

In a seventh preferred implementation of any one of the implementationsof the first preferred aspect above, the attribute corresponding to thesubscription condition includes at least one of the following: areascope; time duration; RLF occurrence frequency; user equipment (UE)measurement item threshold; job identifier information of a signalingtrace job or an MDT job in which an RLF occurs; and identifierinformation of a UE in a signaling trace job or an MDT job in which anRLF occurs.

In an eighth preferred implementation of the seventh implementation ofthe first preferred aspect, when the attribute is the area scope, thevalue of the attribute includes at least one of the following: anidentifier of one or more cells, or a tracking area identifier, or arouting area identifier, or a location area identifier.

In a ninth preferred implementation of any one of the seventhimplementation of the first preferred aspect and the eighthimplementation of the first preferred aspect, the subscription conditioncorresponding to the attribute is: when an RLF occurs on a UE in an areaindicated by the attribute, an RLF report needs to be reported.

In a tenth preferred implementation of the seventh implementation of thefirst preferred aspect, when the attribute is the time duration, theattribute is marked by start time and end time of absolute time, ormarked by start time of absolute time and a duration.

In an eleventh preferred implementation of any one of the seventhimplementation of the first preferred aspect and the tenthimplementation of the first preferred aspect, the subscription conditioncorresponding to the attribute is: when an RLF occurs in the timeduration indicated by the attribute, an RLF report needs to be reported.

In a twelfth preferred implementation of the seventh implementation ofthe first preferred aspect, when the attribute is the RLF occurrencefrequency, the attribute is marked by a duration and the amount of RLFoccurrences.

In a thirteenth preferred implementation of any one of the seventhimplementation of the first preferred aspect and the twelfthimplementation of the first preferred aspect, the subscription conditioncorresponding to the attribute is: when an actual RLF occurrencefrequency is higher than or equal to a frequency indicated by theattribute, an RLF report needs to be reported.

In a fourteenth preferred implementation of the seventh implementationof the first preferred aspect, when the attribute is the UE measurementitem threshold, a value of the attribute includes at least one of thefollowing: a threshold of cell reference signal received power (RSRP)and a threshold of cell reference signal received quality (RSRQ).

In a fifteenth preferred implementation of any one of the seventhimplementation of the first preferred aspect and the fourteenthimplementation of the first preferred aspect, the subscription conditioncorresponding to the attribute is: when a measured value of a UEmeasurement item is non-compliant with a threshold indicated by theattribute, an RLF report needs to be reported.

In a sixteenth preferred implementation of the seventh implementation ofthe first preferred aspect, when the attribute is job identifierinformation of a signaling trace job or an MDT job in which an RLFoccurs, the subscription condition corresponding to the attribute is:when an RLF occurs in a signaling trace job or an MDT job indicated bythe attribute, an RLF report needs to be reported. When the attribute isidentifier information of a UE in a signaling trace job or an MDT job inwhich an RLF occurs, the subscription condition corresponding to theattribute is: when a UE on which an RLF occurs is a UE indicated by theattribute, an RLF report needs to be reported.

In a seventeenth preferred implementation of any one of the seventhimplementation of the first preferred aspect and the sixteenthimplementation of the first preferred aspect, the job identifierinformation is a trace reference value (TR). The identifier informationof the UE includes a combination of a TR and a trace recording sessionreference value (TRSR), or includes a combination of a TR, a TRSR, and acell identifier.

In a second aspect, the present invention provides a method forsubscribing to an RLF report. An IRPAgent configures a subscriptioncondition for an RLF report subscribed to by an IRPManager. The IRPAgentobtains, according to the subscription condition, an RLF report thatsatisfies the subscription condition. The IRPAgent sends the RLF reportthat satisfies the subscription condition to the IRPManager.

In a first preferred implementation of the second preferred aspect, theIRPAgent configures the subscription condition by creating, by theIRPAgent, according to a Create Management Object operation invoked bythe IRPManager, an RLF report subscription subcategory of a subnetcategory or a base station function category. The IRPAgent configuresaccording to a Set Management Object Attributes operation invoked by theIRPManager, an attribute of the created RLF report subscriptionsubcategory to a value of an attribute corresponding to the subscriptioncondition.

In a second preferred implementation of the second preferred aspect, theIRPAgent configures the subscription condition by subscribing to the RLFreport for the IRPManager according to a Subscribe Log operation invokedby the IRPManager, and configuring a filter condition of the SubscribeLog operation to the subscription condition.

In a third preferred implementation of the second preferred aspect, theIRPAgent configures the subscription condition by generating a signalingtrace job according to an Activate Signaling Trace Job operation invokedby the IRPManager. A job type of the signaling trace job is RLFreporting only, and configuring a value of an attribute corresponding tothe subscription condition as an input parameter of the ActivateSignaling Trace Job operation.

In a fourth preferred implementation of the second preferred aspect, theIRPAgent obtains the RLF report by querying according to thesubscription condition, an obtained RLF report sent by a base station inan administrative domain of the IRPAgent, and obtaining the RLF reportthat satisfies the subscription condition. Alternatively, the IRPAgentobtains the RLF report by subscribing, according to the subscriptioncondition, from a base station that satisfies the subscription conditionin an administrative domain of the IRPAgent, and obtaining the RLFreport that satisfies the subscription condition.

In a fifth preferred implementation of any one of the first and fourthimplementation of the second preferred aspect, a mechanism of sending,by the IRPAgent, the RLF report that satisfies the subscriptioncondition to the IRPManager includes a file transfer mechanism.

In a sixth preferred implementation of any one of the second and fourthimplementation of the second preferred aspect, a mechanism of sending,by the IRPAgent, the RLF report that satisfies the subscriptioncondition to the IRPManager includes a notification log mechanism.

In a seventh preferred implementation of any one of the third and fourthimplementation of the second preferred aspect, a mechanism of sending,by the IRPAgent, the RLF report that satisfies the subscriptioncondition to the IRPManager includes a trace result reporting mechanismof a signaling trace job or a trace result reporting mechanism of aminimized drive test MDT job.

In an eighth preferred implementation of any one of the implementationsof the second preferred aspect above, the attribute corresponding to thesubscription condition includes at least one of the following: areascope; time duration; RLF occurrence frequency; user equipment (UE)measurement item threshold; job identifier information of a signalingtrace job or an MDT job in which an RLF occurs; and identifierinformation of a UE in a signaling trace job or an MDT job in which anRLF occurs.

In a ninth preferred implementation of the eighth implementation of thesecond preferred aspect, a value of the attribute includes at least oneof the following: an identifier of one or more cells, or a tracking areaidentifier, or a routing area identifier, or a location area identifierwhen the attribute is an area scope. Alternatively, when the attributeis a time duration, the attribute is marked by start time and end timeof absolute time, or marked by start time of absolute time and aduration. When the attribute is an RLF occurrence frequency, theattribute is marked by a duration and the amount of RLF occurrences.When the attribute is a UE measurement item threshold, a value of theattribute includes at least one of the following: a threshold of cellreference signal received power (RSRP) and a threshold of cell referencesignal received quality (RSRQ).

In a tenth preferred implementation of the ninth implementation of thesecond preferred aspect, the subscription condition corresponding to theattribute includes any one of the following. When the attribute is anarea scope, the subscription condition corresponding to the attributeis: when an RLF occurs on a UE in an area indicated by the attribute, anRLF report needs to be reported. When the attribute is a time duration,the subscription condition corresponding to the attribute is: when anRLF occurs in a time duration indicated by the attribute, an RLF reportneeds to be reported. When the attribute is an RLF occurrence frequency,the subscription condition corresponding to the attribute is: when anactual RLF occurrence frequency is higher than or equal to a frequencyindicated by the attribute, an RLF report needs to be reported. When theattribute is a UE measurement item threshold, the subscription conditioncorresponding to the attribute is: when a measured value of a UEmeasurement item is non-compliant with a threshold indicated by theattribute, an RLF report needs to be reported. When the attribute is jobidentifier information of a signaling trace job or an MDT job in whichan RLF occurs, the subscription condition corresponding to the attributeis: when an RLF occurs in a signaling trace job or an MDT job indicatedby the attribute, an RLF report needs to be reported. When the attributeis identifier information of a UE in a signaling trace job or an MDT jobin which an RLF occurs, the subscription condition corresponding to theattribute is: when a UE on which an RLF occurs is a UE indicated by theattribute, an RLF report needs to be reported.

In a third aspect, the present invention provides a device including aconfiguring unit, adapted to configure a subscription condition for anRLF report, for an IRPAgent. An obtaining unit is adapted to obtain anRLF report that is sent by the IRPAgent and satisfies the subscriptioncondition configured by the configuring unit.

In a first preferred implementation of the third preferred aspect, theconfiguring unit is specifically adapted to: invoke a Create ManagementObject operation for the IRPAgent, for requesting the IRPAgent to createan RLF report subscription subcategory of a subnet category or a basestation function category; and invoke a Set Management Object Attributesoperation for the IRPAgent, for requesting the IRPAgent to configure anattribute of the created RLF report subscription subcategory to a valueof an attribute corresponding to the subscription condition.

In a second preferred implementation of the first preferredimplementation of the third preferred aspect, the obtaining unit isadapted to obtain, in a file transfer mechanism, the RLF report that issent by the IRPAgent and satisfies the subscription condition.

In a third preferred implementation of the third preferred aspect, theconfiguring unit is adapted to invoke a Subscribe Log operation for theIRPAgent, for subscribing to the RLF report from the IRPAgent, andconfigure a filter condition of the Subscribe Log operation to thesubscription condition.

In a fourth preferred implementation of the third preferredimplementation of the third preferred aspect, the obtaining unit isadapted to obtain, in a notification log mechanism, the RLF report thatis sent by the IRPAgent and satisfy the subscription condition.

In a fifth preferred implementation of the third preferred aspect, theconfiguring unit is adapted to invoke an Activate Signaling Trace Joboperation for the IRPAgent, for requesting the IRPAgent to generate asignaling trace job. A job type of the signaling trace job is RLFreporting only. An input parameter of the Activate Signaling Trace Joboperation is a value of an attribute corresponding to the subscriptioncondition.

In a sixth preferred implementation of the fifth preferredimplementation of the third preferred aspect, the obtaining unit isadapted to obtain, in a trace result reporting mechanism of a signalingtrace job or a trace result reporting mechanism of a minimized drivetest MDT job, the RLF report that is sent by the IRPAgent and satisfythe subscription condition.

In a seventh preferred implementation of any one of the implementationsof the third preferred aspect above, the attribute corresponding to thesubscription condition and configured by the configuring unit includesat least one of the following: area scope; time duration; RLF occurrencefrequency; user equipment (UE) measurement item threshold; jobidentifier information of a signaling trace job or an MDT job in whichan RLF occurs; and identifier information of a UE in a signaling tracejob or an MDT job in which an RLF occurs.

In an eighth preferred implementation of any one of the implementationsof the third preferred aspect above, the device is an integrationreference point manager IRPManager.

In a fourth aspect, the present invention provides a device, includes aconfiguring unit adapted to configure a subscription condition for anRLF report subscribed to by an IRPManager. An obtaining unit is adaptedto obtain, according to the subscription condition configured by theconfiguring unit, an RLF report that satisfies the subscriptioncondition. A sending unit is adapted to send the RLF report thatsatisfies the subscription condition and is obtained by the obtainingunit to the IRPManager.

In a first preferred implementation of the fourth preferred aspect, theconfiguring unit is specifically adapted to: create an RLF reportsubscription subcategory of a subnet category or a base station functioncategory according to a Create Management Object operation invoked bythe IRPManager; and configure an attribute of the created RLF reportsubscription subcategory to a value of an attribute corresponding to thesubscription condition.

In a second preferred implementation of the first preferredimplementation of the fourth preferred aspect, the configuring unit isspecifically adapted to subscribe to the RLF report for the IRPManageraccording to a Subscribe Log operation invoked by the IRPManager, andconfigure a filter condition of the Subscribe Log operation to thesubscription condition.

In a third preferred implementation of the first preferredimplementation of the fourth preferred aspect, the configuring unit isadapted to generate a signaling trace job according to an ActivateSignaling Trace Job operation invoked by the IRPManager. A job type ofthe signaling trace job is RLF reporting only. The configuring unit isfurther adapted to configure a value of an attribute corresponding tothe subscription condition as an input parameter of the ActivateSignaling Trace Job operation.

In a fourth preferred implementation of the first preferredimplementation of the fourth preferred aspect, the obtaining unit isadapted to query, according to the subscription condition, an obtainedRLF report sent by a base station in an administrative domain of thedevice, and obtain the RLF report that satisfies the subscriptioncondition. Alternatively, the obtaining unit is adapted to subscribe,according to the subscription condition, from a base station thatsatisfies the subscription condition in an administrative domain of thedevice, and obtain the RLF report that satisfies the subscriptioncondition.

In a fifth preferred implementation of any one of the first and fourthimplementation of the fourth preferred aspect, the sending unit isspecifically adapted to send, in a file transfer mechanism, the RLFreport that satisfies the subscription condition to the IRPManager.

In a sixth preferred implementation of any one of the second and fourthimplementation of the fourth preferred aspect, the sending unit isspecifically adapted to send, in a notification log mechanism, the RLFreport that satisfies the subscription condition to the IRPManager.

In a seventh preferred implementation of any one of the third and fourthimplementation of the fourth preferred aspect, the sending unit isspecifically adapted to send, in a trace result reporting mechanism of asignaling trace job or a trace result reporting mechanism of a minimizeddrive test MDT job. The RLF report that satisfies the subscriptioncondition to the IRPManager.

In an eighth preferred implementation of any one of the implementationsof the fourth preferred aspect above, the attribute corresponding to thesubscription condition and configured by the configuring unit includesat least one of the following: area scope; time duration; RLF occurrencefrequency; user equipment (UE) measurement item threshold; jobidentifier information of a signaling trace job or an MDT job in whichan RLF occurs; and identifier information of a UE in a signaling tracejob or an MDT job in which an RLF occurs.

In a ninth preferred implementation of any one of the implementations ofthe fourth preferred aspect above, where the device is an integrationreference point agent IRPAgent.

The above technical solutions can avoid the case in the prior art that abase station sends an RLF report obtained from a UE, to an IRPManagerthrough an IRPAgent in a best-effort mode, thereby decreasing the loadof information transferred between the IRPManager and the IRPAgent.Moreover, because the RLF report subscription is oriented to a specificmanagement application, the IRPManager does not need to processredundant and useless RLF reports, thereby reducing the processing loadof the IRPManager.

BRIEF DESCRIPTION OF THE DRAWINGS

To illustrate the technical solutions in the embodiments of the presentinvention more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showmerely some embodiments of the present invention, and persons ofordinary skill in the art may still derive other drawings from theseaccompanying drawings without creative efforts.

FIG. 1 is a schematic flowchart of a method for subscribing to an RLFreport according to an embodiment of the present invention;

FIG. 2 is a schematic flowchart of a method for subscribing to an RLFreport according to another embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a device according toanother embodiment of the present invention; and

FIG. 4 is a schematic structural diagram of a device according toanother embodiment of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

To make the objectives, technical solutions, and advantages of theembodiments of the present invention more comprehensible, the followingclearly describes the technical solutions in the embodiments of thepresent invention with reference to the accompanying drawings in theembodiments of the present invention. Apparently, the describedembodiments are merely a part rather than all of the embodiments of thepresent invention. All other embodiments obtained by persons of ordinaryskill in the art based on the embodiments of the present inventionwithout creative efforts shall fall within the protection scope of thepresent invention.

The technical solutions of the present invention may be applied tovarious communication systems, for example, a universal mobiletelecommunications system (UMTS) system, a long term evolution (LTE)system, and so on.

The base station may be a base station controller, such as Radio NetworkController (RNC) in the UMTS system, or may be an evolved base station,such as Evolved NodeB (eNB or eNodeB) in the LTE system, and so on.

In the technical solutions of the present invention, an interfacebetween an IRPManager and an IRPAgent is a northbound interface; theIRPAgent may be a base station or may be an independent entity, so thatthe base station may communicate with the IRPManager through theIRPAgent. The relationship between the IRPManager, the IRPAgent, and thebase station is not described herein. For examples thereof, referencemay be made to the 3GPP standard 32.101 or 32.102.

In addition, the term “and/or” herein indicates only an associationrelationship for describing associated objects, and represents thatthree relationships may exist. For example, A and/or B may represent thefollowing three cases: A exists alone, both A and B exist, and B existsalone. In addition, the symbol “/” in this document usually representsthat associated objects before and after the symbol are in an “or”relationship.

FIG. 1 is a schematic flowchart of a method for subscribing to an RLFreport according to an embodiment of the present invention. As shown inFIG. 1, the method for subscribing to an RLF report in this embodimentmay include the following.

An IRPManager configures a subscription condition for an RLF report, foran IRPAgent.

In this embodiment, an attribute corresponding to the subscriptioncondition includes at least one of the following: area scope(AreaScope), time duration (TimeDuration), RLF occurrence frequency(OccurrenceFrequency), UE measurement item threshold(MeasurementThreshold), job identifier information of a signaling trace(Trace) job or a minimized drive test (MDT) job in which an RLF occurs,and identifier information of a UE in a Trace job or an MDT job in whichan RLF occurs. Specific examples will be described below.

A. Area Scope

The attribute may indicate an area where an RLF report needs to bereported. The value of the attribute may include at least one piece ofidentifier information, for example, a cell identifier, or a trackingarea (TA) identifier, where the identifier is applicable to the casewhere this embodiment is used in an LTE or evolved LTE system, and foranother example, a routing area (RA) identifier or a location area (LA)identifier, where the RA identifier/LA identifier is applicable to thecase where this embodiment is used in the UMTS system, for example, awideband code division multiple access (WCDMA) system or a timedivision-synchronous code division multiple access (TD-SCDMA) system.The cell identifier may be an identifier of a cell, or may beidentifiers of multiple cells (for example, an identifier list formed bymultiple cell identifiers); the tracking area identifier may be anidentifier of a tracking area, or may be identifiers of multipletracking areas; the routing area identifier may be an identifier of arouting area, or may be identifiers of multiple routing areas; and thelocation area identifier may be an identifier of a location area, or mayalso be identifiers of multiple location areas. Optionally, thesubscription condition corresponding to the attribute is: when a UE onwhich an RLF occurs is located in the area scope indicated by theattribute, that is, when an RLF occurs on a UE in the area scopeindicated by the attribute, an RLF report needs to be reported to anIRPManager. For example, if the attribute is the cell identifier of acell, when a UE on which an RLF occurs is located in the cell, anIRPAgent should report the RLF report to the IRPManager. In addition,the attribute may be a default value, indicating the whole public landmobile network (Public Land Mobile Network, PLMN) scope.

B. Time Duration

The attribute may indicate a time duration in which an RLF report needsto be reported. The attribute may be marked by two time relatedvariables, for example, the value of the attribute is made up of twotime values, for example, start time and end time of absolute time, oris made up of a time value and a numeric value, for example, start timeof absolute time and a duration. Optionally, the subscription conditioncorresponding to the attribute may be: when the RLF occurrence time iswithin the time duration indicated by the attribute, an RLF report needsto be reported to an IRPManager.

C. RLF Occurrence Frequency

The attribute may indicate a frequency of RLF occurrences at which anRLF report needs to be reported. The attribute may be marked by a timerelated variable and a variable related to the amount of RLFoccurrences, for example, the value of the attribute is made up of atime value and a numeric value, such as a duration and the amount of RLFoccurrences. Optionally, the subscription condition corresponding to theattribute may be: when an actual RLF occurrence frequency is higher thanor equal to the frequency indicated by the attribute, an RLF reportneeds to be reported to an IRPManager. Assuming that the duration andthe amount of RLF occurrences are 5 minutes and 1000 respectively, theindicated frequency is 1000 RLF events occurring within 5 minutes; thesubscription condition is: when the amount of RLF occurrences within 5minutes is greater than or equal to 1000, an RLF report needs to bereported to the IRPManager.

D. UE Measurement Item Threshold

Optionally, here the UE measurement item threshold may be a threshold ofa UE measurement item threshold in an RLF report. The subscriptioncondition corresponding to the attribute may be: when the measured valueof the UE measurement item is non-compliant with the threshold indicatedby the attribute, an RLF report needs to be reported to an IRPManager;here non-compliance may indicate different cases such as the measuredvalue of the UE measurement item is smaller than or equal to thethreshold indicated by the attribute.

The following describes the value of the attribute and the subscriptioncondition corresponding to the attribute by using examples.

D-1. The value of the attribute is a threshold of reference signalreceived power (RSRP) of a source cell of a UE.

Optionally, the subscription condition corresponding to the attributemay be: when the UE measurement item is an RSRP value of the source cellof the UE, and the measured value of the UE measurement item is smallerthan or equal to the threshold indicated by the attribute, an RLF reportneeds to be reported to the IRPManager.

D-2. The value of the attribute is a threshold of reference signalreceived quality (RSRQ) of a source cell of a UE.

Optionally, the subscription condition corresponding to the attributemay be: when the UE measurement item is an RSRQ value of the source cellof the UE, and the measured value of the UE measurement item is smallerthan or equal to the threshold indicated by the attribute, an RLF reportneeds to be reported to the IRPManager.

D-3. The value of the attribute is a threshold of RSRP of a neighboringcell of the source cell of the UE.

Optionally, the subscription condition corresponding to the attributemay be: when the UE measurement item is an RSRP value of a neighboringcell of the source cell of the UE, and the measured value of the UEmeasurement item is smaller than or equal to the threshold indicated bythe attribute, an RLF report needs to be reported to the IRPManager.

D-4. The value of the attribute is a threshold of RSRQ of a neighboringcell of the source cell of the UE.

Optionally, the subscription condition corresponding to the attributemay be: when the UE measurement item is an RSRQ value of a neighboringcell of the source cell of the UE, and the measured value of the UEmeasurement item is smaller than or equal to the threshold indicated bythe attribute, an RLF report needs to be reported to the IRPManager.

It may be understood that the source cell may be a current cell where anRLF occurs.

Optionally, the measured value of the UE measurement item may be a UEmeasurement record in the RLF report.

E. Job identifier information of a Trace job or an MDT job in which anRLF occurs.

The attribute may indicate information of the job identifier allocatedin the Trace job or MDT job to the UE on which an RLF occurs. The valueof the attribute may be a trace reference value (TR), where the valuemay also be referred to as a trace job reference value.

The subscription condition corresponding to the attribute may be: whenan RLF occurs in the Trace job or MDT job indicated by the attribute, anRLF report needs to be reported to the IRPManager.

F. Identifier information of a UE in a Trace job or an MDT job in whichan RLF occurs.

The attribute may indicate information of the UE identifier allocated inthe Trace job or MDT job to the UE on which an RLF occurs. The value ofthe attribute may be a combination of a TR and a trace recording sessionreference value (TRSR). In a management-based or area-based Trace or MDTjob, the value of the attribute may be a combination of a TR, a TRSR,and a cell identifier.

The subscription condition corresponding to the attribute may be: whenthe UE on which an RLF occurs is the UE indicated by the attribute, anRLF report needs to be reported to the IRPManager.

In this embodiment, if multiple attributes are all configured, that is,values of multiple attributes are configured; the subscription conditionis an intersection of subscription conditions corresponding to variousattributes. To make the method provided by the embodiment of the presentinvention more comprehensible, the following uses two differentscenarios as examples.

Scenario 1: When the IRPManager finds that a large number of “cellunavailable” alarms occur in an area (including following cells: Cell₁,Cell₂, and Cell₃) between Jun. 5 and Jun. 7 in 2010, the IRPManager maysubscribe to reports of RLFs whose occurrence frequency exceeds 1000 incells Cell₁, Cell₂, and Cell₃ between Jun. 5 and Jun. 7 in 2010, so asto provide assistance in analyzing the root cause of a radio networkfault. For example, the subscription condition for an RLF report may beconfigured to: (AreaScope=Cell₁ or Cell₂ or Cell₃) and (TimeDuration isin between {00:00:00, 2010 Jun. 5} and {23:59:59, 2010 Jun. 7}) and(OccurrenceFrequency={5 minutes, 1000}). It may be understood that here“=” means that “the value is”, which is not repeated hereinafter.

Scenario 2: After the IRPManager selects Cell₁ and Cell₂ for creating animmediate (Immediate) MDT job that requires periodic reporting, theIRPManager wishes to obtain RLF reports of RLFs that occur in the wholeimmediate MDT process, so as to perform background associated processingfor the MDT report and RLF report. For example, the subscriptioncondition for an RLF report may be configured to: (AreaScope=Cell₁ andCell₂) and (TraceReference=TR₁), where TRi is information of a jobidentifier allocated to the immediate MDTjob.

Optionally, the IRPManager in this embodiment may configure, in multiplemechanisms, the subscription condition for the RLF report, for theIRPAgent.

For example, first, the IRPManager may invoke a CreateMO (CreateManagement Object) operation for the IRPAgent, for requesting theIRPAgent to create an RLF report subscription (RLFReportingSubscription)subcategory of a subnet category or a base station function category;then the IRPManager may invoke a Set Management Object Attributes(SetMOAttributes) operation for the IRPAgent, for requesting theIRPAgent to configure an attribute of the created RLF reportsubscription subcategory to a value of an attribute corresponding to thesubscription condition.

For another example, the IRPManager may also invoke a Subscribe Log(SubscribeLog) operation for the IRPAgent, for subscribing to the RLFreport from the IRPAgent, and configure a filter condition of theSubscribe Log operation to the subscription condition. For example, acategory of notifications reflecting an RLF event is added to anotification categories (NotificationCategories) parameter in theSubscribe Log operation.

For another example, the IRPManager may also invoke an ActivateSignaling Trace Job (activateTraceJob) operation from a signaling tracejob integration reference point (Trace IRP) for the IRPAgent, forrequesting the IRPAgent to generate a signaling trace job. The job typeof the signaling trace job is RLF reporting only, and an input parameterof the Activate Signaling Trace Job operation is a value of an attributecorresponding to the subscription condition. The operation invoked bythe IRPManager is specifically an Activate Signaling Trace Job operationof the signaling trace job, where the signaling trace job is amanagement object of the IRPManager. It may be understood that, similarto an existing signaling trace job, the IRPAgent may further allocate atrace reference value and a trace recording session reference value tothe generated signaling trace job, where the trace recording sessionreference value may be default without configuration.

102. The IRPManager obtains an RLF report that is sent by the IRPAgentand satisfies the subscription condition.

Optionally, the IRPManager may obtain, in multiple mechanisms, the RLFreport that is sent by the IRPAgent and satisfies the subscriptioncondition.

For example, the IRPManager may obtain, in a file transfer mechanism,the RLF report that is sent by the IRPAgent and satisfies thesubscription condition. Optionally, the specific process is as follows.The IRPManager may receive a notification provided by the IRPAgent usinga “notification file ready” function of a file transfer integrationreference point, and read a subscription result file from a designatedaddress. The file stores the RLF report that satisfies the subscriptioncondition.

For another example, the IRPManager may obtain, in a notification logmechanism, the RLF report that is sent by the IRPAgent and satisfies thesubscription condition. Optionally, the specific process is as follows.The IRPManager may invoke an Export Log Records (ExportLogRecords)operation or Get Log Records (GetLogRecords) operation for the IRPAgentand obtain a notification log. The notification log stores the RLFreport that satisfies the subscription condition.

For another example, the IRPManager may also obtain, in a trace resultreporting mechanism of a signaling trace job or a trace result reportingmechanism of an MDT job, the RLF report that is sent by the IRPAgent andsatisfies the subscription condition. In this case, the IRPManager maystore the obtained RLF report into a trace collection entity (TCE) ofthe IRPManager.

In this embodiment, an IRPManager configures a subscription conditionfor an RLF report, for an IRPAgent, so that the IRPManager can obtain anRLF report that is sent by the IRPAgent and satisfies the subscriptioncondition, which can avoid the case in the prior art that a base stationsends an RLF report obtained from a UE, to an IRPManager through anIRPAgent in a best-effort mode, thereby decreasing the load ofinformation transferred between the IRPManager and the IRPAgent.Moreover, because the RLF report subscription is oriented to a specificmanagement application, the IRPManager does not need to processredundant and useless RLF reports, thereby reducing the processing loadof the IRPManager.

Optionally, the IRPAgent in this embodiment may obtain, before step 102,the RLF report that satisfies the subscription condition, which is notfurther described herein. For details, reference may be made to step 202and its example in the embodiment shown in FIG. 2.

FIG. 2 is a schematic flowchart of a method for subscribing to an RLFreport according to another embodiment of the present invention. Asshown in FIG. 2, the method for subscribing to an RLF report in thisembodiment may include the following.

201. An IRPAgent configures a subscription condition for an RLF reportsubscribed to by an IRPManager.

An attribute corresponding to the subscription condition may include atleast one of the following: area scope (AreaScope), time duration(TimeDuration), RLF occurrence frequency (OccurrenceFrequency), UEmeasurement item threshold (MeasurementThreshold), job identifierinformation of a Trace job or an MDT job in which an RLF occurs, andidentifier information of a UE in a Trace job or an MDT job in which anRLF occurs.

The attributes and subscription conditions corresponding to theattributes are not further described herein. For examples thereof,reference may be made to the related content in the embodimentcorresponding to FIG. 1.

Optionally, the IRPAgent may configure, in multiple mechanisms, thesubscription condition for an RLF report subscribed to by theIRPManager.

For example, first, the IRPAgent may create an RLF report subscriptionsubcategory of a subnet category or a base station function categoryaccording to a Create Management Object operation invoked by theIRPManager; and then the IRPAgent may configure, according to a SetManagement Object Attributes operation invoked by the IRPManager, anattribute of the created RLF report subscription subcategory to a valueof an attribute corresponding to the subscription condition.

For another example, the IRPAgent may further subscribe to the RLFreport for the IRPManager according to a Subscribe Log operation invokedby the IRPManager, and configure a filter condition of the Subscribe Logoperation to the subscription condition. For example, a category ofnotifications reflecting an RLF event is added to a notificationcategories parameter in the Subscribe Log operation.

For another example, the IRPAgent may also generate a signaling tracejob for the IRPManager according to an Activate Signaling Trace Job(activateTraceJob) operation invoked by the IRPManager, where the jobtype of the signaling trace job is RLF reporting only, and configure thevalue of the attribute corresponding to the subscription condition as aninput parameter of the Activate Signaling Trace Job operation. It may beunderstood that, similar to an existing signaling trace job, theIRPAgent may further allocate a trace reference value (Trace Reference)and a trace recording session reference value (Trace Recording SessionReference) to the generated signaling trace job, where the tracerecording session reference value may be default without configuration.

202. The IRPAgent obtains, according to the subscription condition, anRLF report that satisfies the subscription condition.

Optionally, the IRPAgent may obtain, in multiple mechanisms according tothe subscription condition, the RLF report that satisfies thesubscription condition.

For example, the IRPAgent queries, according to the subscriptioncondition, an obtained RLF report sent by a base station in anadministrative domain of the IRPAgent. The IRPAgent obtains the RLFreport that satisfies the subscription condition. The base station maybe understood as a source base station; the source base station sendsall obtained RLF reports to the corresponding IRPAgent. The IRPAgentqueries, according to the subscription condition, the obtained RLFreports sent by the base station in the administrative domain of theIRPAgent, and obtains the RLF report that satisfies the subscriptioncondition.

For another example, the IRPAgent subscribes, according to thesubscription condition, from a base station that satisfies thesubscription condition in the administrative domain of the IRPAgent, andobtains the RLF report that satisfies the subscription condition. Thebase station may be understood as a source base station, or may beunderstood as a target base station. The base station sends, accordingto the subscription condition of the IRPAgent, the RLF report thatsatisfies the subscription condition to the corresponding IRPAgent; andthe IRPAgent obtains the RLF report that satisfies the subscriptioncondition.

The following describes how to query the RLF reports and obtain the RLFreport that satisfies the subscription condition by using an example.

The content of the RLF report may include but is not limited to at leastone of the following. The content of the RLF report may include ameasured value of RSRP/RSRQ of the source cell of the UE when an RLFoccurs. The content of the RLF report may include a measured value ofRSRP/RSRQ of a neighboring cell of the source cell of the UE when an RLFoccurs. The neighboring cell may be any one of the following: anintra-frequency neighboring cell, an inter-frequency neighboring cell,and an inter-system neighboring cell. The content of the RLF report mayinclude UE location information. The content of the RLF report mayinclude a serving cell identifier of the UE. The serving cell identifiermay include but is not limited to at least one of a cell globalidentifier (CGI) of a cell where an RLF occurs on the UE, a cell (targetcell) where the UE reestablishes an RRC connection, and a CGI of a cellbefore a handover of the UE. The content of the RLF report may include ajob identifier information of a signaling trace job or an MDT job inwhich an RLF occurs, for example, a TR. The content of the RLF reportmay include a identifier information of the UE in a signaling trace jobor an MDT job in which an RLF occurs, for example, a combination of a TRand a TRSR.

The IRPAgent or base station may query the obtained RLF reports to seewhich RLF reports satisfy the subscription condition, and report the RLFreports. For example, according to the time of obtaining the RLFreports, the IRPAgent or base station estimates the RLF occurrence time,and determines whether the RLF reports satisfy the subscriptioncondition corresponding to attribute A. The time obtained by advancingthe time of obtaining RLF reports by a duration (such as 4s) may be usedas the estimated RLF occurrence time. For another example, the IRPAgentor base station makes statistics according to the obtained RLF reports,for example, makes statistics of the actual occurrence frequency of anRLF event in the base station or cell scope, and determines whether thesubscription condition corresponding to attribute D is satisfied. Foranother example, in the case that an RLF occurs in a signaling trace jobor an MDT job, the IRPAgent or base station judges the obtained RLFreports; when the job identifier information in an RLF report is thesame as the value of attribute E or falls within the value range ofattribute E, the RLF report satisfies the subscription conditioncorresponding to attribute E. For another example, in the case that anRLF occurs in a signaling trace job or an MDT job, the IRPAgent or basestation judges the obtained RLF reports; when the UE identifier in anRLF report is the same as the value of attribute F or falls within thevalue range of attribute F, the RLF report satisfies the subscriptioncondition corresponding to attribute F.

203. The IRPAgent sends the RLF report that satisfies the subscriptioncondition to the IRPManager.

Optionally, the IRPAgent may send, in multiple mechanisms, the RLFreport that satisfies the subscription condition to the IRPManager.

For example, the IRPAgent may send, in a file transfer mechanism, theRLF report that satisfies the subscription condition to the IRPManager.That is, the IRPAgent sends, through a file transfer integrationreference point, the RLF report that satisfies the subscriptioncondition to the IRPManager. Optionally, the specific process is asfollows: After the IRPAgent obtains the RLF report that satisfies thesubscription condition, the IRPAgent may store the RLF report thatsatisfies the subscription into a file, and notify the IRPManager byusing a “notification file ready” function of the file transferintegration reference point; and the IRPManager reads a subscriptionresult file from a designated address.

For another example, the IRPAgent may send, in a notification logmechanism, the RLF report that satisfies the subscription condition tothe IRPManager. That is, the IRPAgent sends, by using a function of anotification log integration reference point, the RLF report thatsatisfies the subscription condition to the IRPManager. Optionally, thespecific process is as follows: After the IRPAgent obtains the RLFreport that satisfies the subscription condition, the IRPAgent may storethe RLF report that satisfies the subscription condition into anotification log, and send the notification log to the IRPManageraccording to an Export Log Records operation or a Get Log Recordsoperation invoked by the IRPManager.

For another example, the IRPAgent may also send, in a trace resultreporting mechanism of a signaling trace job or a trace result reportingmechanism of an MDT job, the RLF report that satisfies the subscriptioncondition to the IRPManager. In this case, the IRPManager further storesthe obtained RLF report into a TCE of the IRPManager.

In this embodiment, the IRPAgent configures the subscription conditionfor an RLF report subscribed to by the IRPManager so that the IRPAgentcan obtain, according to the subscription condition, an RLF report thatsatisfies the subscription condition and send the RLF report to theIRPManager, which can avoid the case in the prior art that a basestation sends an RLF report obtained from a UE, to an IRPManager throughan IRPAgent in a best-effort mode, thereby decreasing the load ofinformation transferred between the IRPManager and the IRPAgent.Moreover, because the RLF report subscription is oriented to a specificmanagement application, the IRPManager does not need to processredundant and useless RLF reports, thereby reducing the processing loadof the IRPManager.

It should be noted that, for ease of description, the foregoing methodembodiments are all described as a series of actions. Persons skilled inthe art should understand that the present invention is not limited tothe sequence of actions described herein, and that according to thepresent invention. Some steps may be performed in other sequences or atthe same time. Persons skilled in the art should also know that theembodiments in the specification are exemplary embodiments and thatactions and modules involved in these embodiments are not necessarilyrequired for the present invention.

In the foregoing embodiments, the description in each embodiment has itsown focus. For the part that is not described in a certain embodiment,reference may be made to relevant descriptions in other embodiments.

FIG. 3 is a schematic structural diagram of a device according toanother embodiment of the present invention. As shown in FIG. 3, thedevice in this embodiment may include a configuring unit 31 and anobtaining unit 32. The configuring unit 31 is adapted to configure asubscription condition for an RLF report, for an IRPAgent. The obtainingunit 32 is adapted to obtain an RLF report that is sent by the IRPAgentand satisfy the subscription condition configured by the configuringunit 31.

The device provided by this embodiment may be but is not limited to theIRPManager.

Any function of the IRPManager in the embodiment corresponding to FIG. 1and FIG. 2 may be implemented by the device provided by this embodiment.

Optionally, the configuring unit 31 in this embodiment may invoke aCreate Management Object operation for the IRPAgent, for requesting theIRPAgent to create an RLF report subscription subcategory of a subnetcategory or a base station function category; and invoke a SetManagement Object Attributes operation for the IRPAgent, for requestingthe IRPAgent to configure an attribute of the created RLF reportsubscription subcategory to a value of an attribute corresponding to thesubscription condition. Optionally, the obtaining unit 32 in thisembodiment may be specifically adapted to obtain, in a file transfermechanism, the RLF report that is sent by the IRPAgent and satisfies thesubscription condition.

Optionally, the configuring unit 31 in this embodiment may furtherinvoke a Subscribe Log operation for the IRPAgent, for subscribing tothe RLF report from the IRPAgent, and configure a filter condition ofthe Subscribe Log operation to the subscription condition. Optionally,the obtaining unit 32 in this embodiment may be specifically furtheradapted to obtain, in a notification log mechanism, the RLF report thatis sent by the IRPAgent and satisfies the subscription condition.

Optionally, the configuring unit 31 in this embodiment may furtherinvoke an Activate Signaling Trace Job (activateTraceJob) operation froma signaling trace job integration reference point (Trace IRP) for theIRPAgent, for requesting the IRPAgent to generate a signaling trace job.The job type of the signaling trace job is RLF reporting only. An inputparameter of the Activate Signaling Trace Job operation is a value of anattribute corresponding to the subscription condition. The operationinvoked by the IRPManager may be an Activate Signaling Trace Joboperation of the signaling trace job. The signaling trace job is amanagement object of the IRPManager. Optionally, the obtaining unit 32in this embodiment may be specifically further adapted to obtain, in atrace result reporting mechanism of a signaling trace job or a traceresult reporting mechanism of an MDT job, the RLF report that is sent bythe IRPAgent and satisfies the subscription condition.

The attribute corresponding to the subscription condition configured bythe configuring unit 31 may include at least one of the following: areascope, time duration, RLF occurrence frequency, UE measurement itemthreshold, job identifier information of a Trace job or an MDT job inwhich an RLF occurs, and identifier information of a UE in a Trace jobor an MDT job in which an RLF occurs.

The attributes and subscription conditions corresponding to theattributes are not further described herein. For examples thereof,reference may be made to the related content in the embodimentcorresponding to FIG. 1.

In the device provided by this embodiment, a configuring unit configuresa subscription condition for an RLF report, for an IRPAgent, so that anobtaining unit can obtain an RLF report that is sent by the IRPAgent andsatisfies the subscription condition, which can avoid the case in theprior art that a base station sends an RLF report obtained from a UE, toan IRPManager through an IRPAgent in a best-effort mode, therebydecreasing the load of information transferred between the IRPManagerand the IRPAgent. Moreover, because the RLF report subscription isoriented to a specific management application, the IRPManager does notneed to process redundant and useless RLF reports, thereby reducing theprocessing load of the IRPManager.

FIG. 4 is a schematic structural diagram of a device according toanother embodiment of the present invention. As shown in FIG. 4, thedevice in this embodiment may include a configuring unit 41, anobtaining unit 42, and a sending unit 43. The configuring unit 41 isadapted to configure a subscription condition for an RLF reportsubscribed to by an IRPManager. The obtaining unit 42 is adapted toobtain, according to the subscription condition configured by theconfiguring unit 41, an RLF report that satisfies the subscriptioncondition; and the sending unit 43 is adapted to send the RLF reportthat satisfies the subscription condition and is obtained by theobtaining unit 42 to the IRPManager.

The device provided by this embodiment may be but is not limited to theIRPAgent.

Any function of the IRPAgent in the embodiment corresponding to FIG. 1and FIG. 2 may be implemented by the device provided by this embodiment.

Optionally, the configuring unit 41 in this embodiment may specificallycreate an RLF report subscription subcategory of a subnet category or abase station function category according to a Create Management Objectoperation invoked by the IRPManager; and configure, according to a SetManagement Object Attributes operation invoked by the IRPManager, anattribute of the created RLF report subscription subcategory to a valueof an attribute corresponding to the subscription condition. Optionally,the sending unit 43 in this embodiment may be specifically adapted tosend, in a file transfer mechanism, the RLF report that satisfies thesubscription condition to the IRPManager.

Optionally, the configuring unit 41 in this embodiment may furtherspecifically subscribe to the RLF report for the IRPManager according toa Subscribe Log operation invoked by the IRPManager, and configure afilter condition of the Subscribe Log operation to the subscriptioncondition. Optionally, the sending unit 43 in this embodiment may bespecifically adapted to send, in a notification log mechanism, the RLFreport that satisfies the subscription condition to the IRPManager.

Optionally, the configuring unit 41 in this embodiment may bespecifically further adapted to generate a signaling trace job accordingto an Activate Signaling Trace Job (activateTraceJob) operation invokedby the IRPManager, where the job type of the signaling trace job is RLFreporting only, and configure an input parameter of the ActivateSignaling Trace Job operation to a value of an attribute correspondingto the subscription condition. Optionally, the sending unit 43 in thisembodiment may be specifically further adapted to send, in a traceresult reporting mechanism of a signaling trace job or a trace resultreporting mechanism of an MDT job, the RLF report that satisfies thesubscription condition to the IRPManager.

The attribute corresponding to the subscription condition configured bythe configuring unit may include at least one of the following: areascope, time duration, RLF occurrence frequency, UE measurement itemthreshold, job identifier information of a Trace job or a minimizeddrive test MDT job in which an RLF occurs, and identifier information ofa UE in a Trace job or an MDT job in which an RLF occurs.

The attributes and subscription conditions corresponding to theattributes are not further described herein. For examples thereof,reference may be made to the related content in the embodimentcorresponding to FIG. 1.

Specifically, the obtaining unit 42 in this embodiment may query,according to the subscription condition, obtained RLF reports sent by abase station in an administrative domain of the device, and obtain theRLF report that satisfies the subscription condition; or subscribe,according to the subscription condition, from a base station thatsatisfies the subscription condition in an administrative domain of thedevice, and obtain the RLF report that satisfies the subscriptioncondition.

In the device provided by this embodiment, a configuring unit configuresa subscription condition for an RLF report subscribed to by anIRPManager, so that an obtaining unit can obtain, according to thesubscription condition, an RLF report that satisfies the subscriptioncondition, and a sending unit sends the RLF report to the IRPManager,which can avoid the case in the prior art that a base station sends anRLF report obtained from a UE, to an IRPManager through an IRPAgent in abest-effort mode, thereby decreasing the load of information transferredbetween the IRPManager and the IRPAgent. Moreover, because the RLFreport subscription is oriented to a specific management application,the IRPManager does not need to process redundant and useless RLFreports, thereby reducing the processing load of the IRPManager.

It may be clearly learned by persons skilled in the art that, to achievethe purpose of convenient and brief description, for a detailed workingprocess of the foregoing devices and units, reference may be made to thecorresponding process in the foregoing method embodiments, which is notdescribed herein again.

In the several embodiments provided in this application, it should beunderstood that the disclosed system, device, and method may beimplemented in other manners. For example, the foregoing describeddevice embodiments are merely exemplary. For example, the unit divisionis merely a logical function division and may be other divisions inactual implementation. For example, multiple units or components can becombined or integrated into another system, or some features can beignored or not performed. In addition, the displayed or discussed mutualcouplings or direct couplings or communication connections may beimplemented through some interfaces. The indirect couplings orcommunication connections between the devices or units may beimplemented in electronic, mechanical or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,that is, may be located in one position, or may be distributed on aplurality of network units. A part or all of the units may be selectedaccording to actual needs to achieve the objectives of the solutions ofthe embodiments.

In addition, functional units in the embodiments of the presentinvention may be integrated into one processing unit, or each of theunits may exist alone physically, or two or more units are integratedinto one unit. The integrated unit may be implemented through hardware,or may be implemented in a form of hardware plus a software functionalmodule.

The integrated unit implemented in the form of software functional unitmay be stored in a computer readable storage medium. The softwarefunctional unit is stored in a storage medium, and contains severalinstructions used to instruct computer equipment (for example, apersonal computer, a server, or network equipment) to perform a part ofthe steps of the methods according to the embodiments of the presentinvention. The foregoing storage medium includes: any medium that canstore program codes, such as a USB flash disk, a removable hard disk, aread-only memory (ROM), a random access memory (RAM), a magnetic disk,or an optical disk.

Finally, it should be noted that the foregoing embodiments are merelyintended for describing the technical solutions of the present inventionrather than limiting the present invention. Although the presentinvention is described in detail with reference to the foregoingembodiments, persons of ordinary skill in the art should understand thatthey may still make modifications to the technical solutions describedin the foregoing embodiments, or make equivalent replacements to sometechnical features thereof as long as such modifications andreplacements do not cause the essence of the corresponding technicalsolutions to depart from the scope of the technical solutions of theembodiments of the present invention.

What is claimed is:
 1. A method for subscribing to a radio link failure(RLF) report, comprising: generating, by an integration reference pointagent (IRPAgent), a signaling trace job according to an active signalingtrace job operation, wherein a job type of the signaling trace job isRLF reporting only, and wherein an input parameter of the activatesignaling trace job operation is a value of an attribute correspondingto a subscription condition of the RLF report; obtaining, by theIRPAgent according to the subscription condition, an RLF report thatsatisfies the subscription condition; and sending, by the IRPAgent, theRLF report that satisfies the subscription condition to an integrationreference point manager (IRPManager).
 2. The method according to claim1, wherein obtaining, by the IRPAgent according to the subscriptioncondition, the RLF report that satisfies the subscription conditioncomprises: querying, by the IRPAgent according to the subscriptioncondition, an obtained RLF report sent by a base station in anadministrative domain of the IRPAgent; and obtaining the RLF report thatsatisfies the subscription condition.
 3. The method according to claim1, wherein obtaining, by the IRPAgent according to the subscriptioncondition, the RLF report that satisfies the subscription conditioncomprises: subscribing, by the IRPAgent according to the subscriptioncondition, from a base station that satisfies the subscription conditionin an administrative domain of the IRPAgent; and obtaining, by theIRPAgent, the RLF report that satisfies the subscription condition. 4.The method according to claim 1, wherein a mechanism of sending, by theIRPAgent, the RLF report that satisfies the subscription condition tothe IRPManager comprises a trace result reporting mechanism of asignaling trace job or a trace result reporting mechanism of a minimizeddrive test (MDT) job.
 5. The method according to claim 4, wherein theattribute corresponding to the subscription condition comprises areascope.
 6. The method according to claim 1, wherein the attributecorresponding to the subscription condition comprises area scope.
 7. Themethod according to claim 6, wherein a value of the attribute comprisesat least one of the following: an identifier of one or more cells, atracking area identifier, a routing area identifier, and a location areaidentifier.
 8. The method according to claim 1, wherein a value of theattribute comprises at least one of the following: an identifier of oneor more cells, a tracking area identifier, a routing area identifier,and a location area identifier.
 9. The method according to claim 1,wherein the subscription condition corresponding to the attributecomprises: reporting a RLF report when an RLF occurs on a UE in an areaindicated by the attribute.
 10. An integration reference point agent(IRPAgent), comprising: a processor; a non-transitory computer-readablestorage medium storing a program to be executed by the processor, theprogram including instructions for: generating a signaling trace jobaccording to an active signaling trace job operation, wherein a job typeof the signaling trace job is RLF reporting only, wherein an inputparameter of the activate signaling trace job operation is a value of anattribute corresponding to a subscription condition of the RLF report;obtaining an RLF report that satisfies the subscription conditionaccording to the subscription condition; and sending the RLF report thatsatisfies the subscription condition to an integration reference pointmanager (IRPManager).
 11. The IRPAgent according to claim 10, whereinthe program further includes instructions for: querying an obtained RLFreport sent by a base station in an administrative domain of theIRPAgent according to the subscription condition; and obtaining the RLFreport that satisfies the subscription condition.
 12. The IRPAgentaccording to claim 10, wherein the program further includes instructionsfor: subscribing from a base station that satisfies the subscriptioncondition in an administrative domain of the IRPAgent; and obtaining theRLF report that satisfies the subscription condition.
 13. The IRPAgentaccording to claim 10, wherein a mechanism of sending the RLF reportthat satisfies the subscription condition to the IRPManager comprises atrace result reporting mechanism of a signaling trace job or a traceresult reporting mechanism of a minimized drive test (MDT) job.
 14. TheIRPAgent according to claim 13, wherein the attribute corresponding tothe subscription condition comprises area scope.
 15. The IRPAgentaccording to claim 10, wherein the attribute corresponding to thesubscription condition comprises area scope.
 16. The IRPAgent accordingto claim 15, wherein a value of the attribute comprises at least one ofthe following: an identifier of one or more cells, a tracking areaidentifier, a routing area identifier, and a location area identifier.17. The IRPAgent according to claim 10, wherein a value of the attributecomprises at least one of the following: an identifier of one or morecells, a tracking area identifier, a routing area identifier, and alocation area identifier.
 18. The IRPAgent according to claim 10,wherein the subscription condition corresponding to the attributecomprises: reporting a RLF report when an RLF occurs on a UE in an areaindicated by the attribute.